home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.9 KB | 44 lines | [TEXT/GEOL] |
- Item forwarded by FRED.FORSMAN to SUMIT
-
- Item 1308367 8-Nov-90 11:49PST
-
- From: D6502 Focal Point Sys, M L Kary,PRT
-
- To: MACAPP.TECH$ MacApp Technical
-
- cc: BETA Beta, Edward Anuff,PRT
-
- Sub: Need help with SADE, C++
-
- Hello folks,
-
- I am trying to use SADE to debug C++ with MacApp. For my style of debugging,
- being able to step through the source code a line at a time and examine
- variables and data structures is absolutely essential. Sure, you can insert
- print and break statements into the source, but that's a painful approach.
- Also, when so much is pre-compiled, as is MacApp, and compiling is so slow,
- there's got to be a better way. Maybe I'm just spoiled from using the Think C
- debugger for so long.
-
- My problem with SADE is that I can't get it to step into MacApp. I have built
- my application with -sym, and that seems to be okay. I believe that it must be
- linking with the version of MacApp that was built with -sym. I used the
- 'sourcepath' command to tell SADE where my source files are and where the
- MacApp source and interface files are, namely the 'Libraries' and the
- 'PInterfaces' folders. I typed the 'sourcepath' command with no arguments, to
- confirm that SADE knows where the source is. I did all the 'setupStepMethod'
- stuff that you're supposed to do (I think). I can step into one of my own C++
- methods just fine. But when I try to step into a MacApp method, such as
- TApplication.IApplication, I get an assembly language disassembly in my
- worksheet. Selecting the routine name and using the 'Show Source' command
- gives me the message that the source cannot be found.
-
- I assume that it should be possible to use SADE to step through MacApp,
- although I read somewhere that there is a problem when there is more than 64K
- lines of code. Does anyone have any idea what I might be doing wrong?
-
- Thanks,
- Loran Kary
- Focal Point Systems D6502
-
-